Skip to content

Conversation

@alebcay
Copy link
Member

@alebcay alebcay commented Oct 18, 2025

  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

  • Confirm that current build process results in build/publish failure by adding steps in test (control case).
  • Try setting /p:PortableBuild=true as a fix. If build and modified test succeeds, download the resulting bottles and see how linkage differs.
  • Try setting /p:BundleNativeAotCompiler=false as a fix. If build and modified test succeeds, confirm no change in linkage and that the test is indeed pulling AOT compiler from NuGet.

@github-actions github-actions bot added long build Set a long timeout for formula testing icu4c ICU use is a significant feature of the PR or issue labels Oct 18, 2025
@alebcay alebcay added the CI-linux-self-hosted Build on Linux self-hosted runner label Oct 18, 2025
@cho-m cho-m added the CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. label Oct 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI-linux-self-hosted Build on Linux self-hosted runner CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. icu4c ICU use is a significant feature of the PR or issue long build Set a long timeout for formula testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants